fix: Argument target_group_arn
should not be defined if listener type is forward
and traffic needs to be routed to multiple target groups
#300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #299
Motivation and Context
Fixes bug that currently makes weighted target groups not to work as expected, documented more in-depth in the issue above.
Breaking Changes
No
How Has This Been Tested?
I have tested this module with a listener that is using weighted target groups, like the one provided in the examples
terraform-aws-alb/examples/complete-alb/main.tf
Lines 82 to 98 in cb8e43d
Now, when more than 1 target group is defined, the default
target_group_arn
is removed, and the target groups are configured as expected in theforward
blockFurther apply's don't keep on trying to configure the forward section indefinitely.